Aerospike Health and Performance Report

Executive Summary

This report provides a health assessment for the Aerospike cluster consisting of 5 nodes. Analysis identified 50,720,801 “Delete Not Found” events, suggesting application-side logic gaps.

NoteTAM Overview

The cluster is stable, but high DNF rates indicate unnecessary IOPS pressure. Reviewing application “blind delete” patterns is the primary recommendation.

Cluster Status Overview

WarningConfig Symmetry

Detected 365 configuration drifts across the cluster.

WarningDelete Not Found

Detected 50,720,801 ‘Delete Not Found’ events across 5 nodes.

WarningConfig Drift

The static aerospike.conf file was not found in the collectinfo bundle.

Performance and Utilization

Disk Usage % by Node

Client Connections

Observations and Remediation

1.b: ENA Support Check

ENA Telemetry Missing: OS-level statistics were not found in this bundle.

Recommendation: To retrieve this data, run ‘collectinfo’ as root or use ‘asadm –lsmod –ethtool’. Manually verify with: ‘ethtool -i eth0’.

---

1.c: Version Consistency

Telemetry not yet ingested.

Recommendation: Review cluster telemetry and application logs for further investigation.

---

3.a: Config Symmetry

Detected 365 configuration drifts across the cluster.

Recommendation: Check the Technical Details section to identify which specific parameters (e.g. memory, timeouts) differ.

---

3.b: Config Drift

The static aerospike.conf file was not found in the collectinfo bundle.

Recommendation: Cannot perform drift analysis (Runtime vs. Static). To enable this check in the future, run: ‘asadm -e “collectinfo –cf /etc/aerospike/aerospike.conf”’

---

4.b: Read Not Found

Detected 4,068 ‘Read Not Found’ events. This is often normal for application cache-miss workflows.

Recommendation: If the application expects all records to exist, investigate potential expiration or eviction issues.

---

4.c: Delete Not Found

Detected 50,720,801 ‘Delete Not Found’ events across 5 nodes.

Recommendation: This suggests the application is attempting to delete records that do not exist (Blind Deletes). Review application logic.

---

Appendix: All Tests Performed

Check Name	Status
1.a: Service Error Skew	✅ PASS
1.b: ENA Support Check	⚠️ INFO
1.c: Version Consistency	⚠️ INFO
2.a: SIndex on Flash	✅ PASS
2.b: Sprig Limit Warning	✅ PASS
2.c: Storage Deadlock Risk	✅ PASS
2.d: Disk HWM Check	✅ PASS
2.e: Memory HWM Check	✅ PASS
3.a: Config Symmetry	⚠️ WARNING
3.b: Config Drift	⚠️ ⚠️ DATA MISSING
4.a: Hot Key Detection	✅ PASS
4.b: Read Not Found	⚠️ INFO
4.c: Delete Not Found	⚠️ WARNING

TAM Technical Details

Node Statistics (Sample)

node_id	metric	value
10.94.173.12:3000	service.heartbeat_connections_closed	12.000
10.94.173.43:3000	service.cluster_generation	8.000
10.94.173.82:3000	service.fabric_connections_closed	30.000
10.94.173.40:3000	service.fabric_rw_send_rate	322855.000
10.94.173.73:3000	service.cluster_clock_skew_ms	0.000
10.94.173.73:3000	service.cluster_clock_skew_stop_writes_sec	0.000
10.94.173.43:3000	service.fabric_connections_closed	65.000
10.94.173.82:3000	service.batch_index_proto_uncompressed_pct	0.002
10.94.173.40:3000	service.client_connections	1315.000
10.94.173.40:3000	service.uptime	7079149.000

---

Aerospike Health Analyzer | Version: 1.3.0 | Generated: 2026-02-07 17:23